home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20000217-20000824
/
000116_news@columbia.edu _Tue Mar 14 17:03:10 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2000-08-23
|
3KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id RAA17894
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 14 Mar 2000 17:03:09 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id QAA14203
for kermit.misc@watsun.cc.columbia.edu; Tue, 14 Mar 2000 16:36:15 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Subject: Re: Sockets programming: telnet problem.
Date: 14 Mar 2000 21:36:14 GMT
Organization: Columbia University
Message-ID: <8ambce$dro$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <8am990$9jj$1@nnrp1.deja.com>, <jrc@lhutz.demon.co.uk> wrote:
: ...
: Thanks! While I will take a look at C-Kermit, I am still writing my
: ground up code simply for my own experience and sense of
: satisfaction.
:
: I really am VERY curious as to what the probelm is and why I'm not
: seeing those prompts until after input, so I really would be very
: appreciative if someone could still answer my question via email
: (jrc@aardsets.com).
:
: Thanks very much for the information, and rest assured, I WILL take
: a look at that, but I'm also determined to complete what I've started.
:
Sure, but be warned: it's a slippery slope. Telnet is not a simple
protocol, at least not any more. It started out as RFC854 in 1983 and
has grown ever since. A current search of the RFC database for "telnet"
turns up 107 references.
Unfortunately, all too many people crank out ad-hoc Telnet clients by
(a) trial and error, (b) asking somebody how to do it and then acting on
bad advise, (c) copying some code they found by searching the Internet,
or (d) following RFC854 but nothing else. All of these, including (d),
are likely not to work when fielded against the variety of Telnet servers,
ancient to modern, that exist today. Doing it right is a long, hard, big
job, and the job doesn't end when just one test case works.
While I'm at it, I should mention that more than a few Telnet servers
violate the IETF standards. Unfortunately, many writers of Telnet
implementations don't know this, and so tailor their programs to work with
the faulty servers, thus propogating their errors and making matters more
difficult for everybody.
Again, see:
http://www.columbia.edu/kermit/telnet.html
to get an idea of some of the considerations that must go into writing
modern and correct Telnet sofware, especially the later sections that deal
with broken Telnet implementations.
- Frank